-
-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for HTML renderings of room topics #2272
Conversation
Based on extensible events as defined in [MSC1767] Relates to: element-hq/element-web#5180 Signed-off-by: Johannes Marbach <johannesm@element.io> [MSC1767]: matrix-org/matrix-spec-proposals#1767
Codecov Report
@@ Coverage Diff @@
## develop #2272 +/- ##
========================================
Coverage 59.75% 59.75%
========================================
Files 91 92 +1
Lines 16450 16455 +5
Branches 3796 3799 +3
========================================
+ Hits 9829 9833 +4
- Misses 6621 6622 +1
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this side lgtm
Could I get a pass with "only" 73% coverage? I think I've covered the meaningful bits with tests. |
The gate being 80% is actually considered low, James wanted the gate for the js-sdk to be 100% given it is a reusable SDK. The bits in topic.ts are fully covered, content-helpers is lacking one line and client.ts is at 59.3%. https://sonarcloud.io/code?id=matrix-js-sdk&pullRequest=2272&selected=matrix-js-sdk%3Asrc%2Fcontent-helpers.ts&line=217 If you cover either of the above you should hit the gate. Are there any parts here which are infeasible to cover for some reason? |
Could you also please pull latest develop, some of the checks aren't running seemingly |
I suppose not infeasible, no. The main untested chunk
Hm, I had merged in develop just last night. 🤔 I'll merge it again when working on the tests. Hopefully that fixes it. |
The added backwards compatibility overload is certainly worth testing, those are super fragile. |
(Adding the label re-ran the missing CI job) |
Hm, something's wrong. I've added tests for
When I click through, it lists a lot of uncovered lines in "new" code for files that I haven't actually touched, like 81 lines in @t3chguy any idea what's wrong here? |
I wonder if it just doesn't understand merge commits... |
Not sure what happened here - #2366 was unaffected, showing 81.6% covg before & after the merge commit |
Skipping Sonar check due to weirdness, coverage is appropriate already |
Thanks @t3chguy! |
* Implement changes to MSC2285 (private read receipts) ([\matrix-org#2221](matrix-org#2221)). * Add support for HTML renderings of room topics ([\matrix-org#2272](matrix-org#2272)). * Add stopClient parameter to MatrixClient::logout ([\matrix-org#2367](matrix-org#2367)). * registration: add function to re-request email token ([\matrix-org#2357](matrix-org#2357)). * Remove hacky custom status feature ([\matrix-org#2350](matrix-org#2350)). * Remove default push rule override for MSC1930 ([\matrix-org#2376](matrix-org#2376)). Fixes element-hq/element-web#15439. * Tweak thread creation & event adding to fix bugs around relations ([\matrix-org#2369](matrix-org#2369)). Fixes element-hq/element-web#22162 and element-hq/element-web#22180. * Prune both clear & wire content on redaction ([\matrix-org#2346](matrix-org#2346)). Fixes element-hq/element-web#21929. * MSC3786: Add a default push rule to ignore `m.room.server_acl` events ([\matrix-org#2333](matrix-org#2333)). Fixes element-hq/element-web#20788.
For matrix-org/matrix-react-sdk#8215
MSC: matrix-org/matrix-spec-proposals#3765
Relates to element-hq/element-web#5180
This introduces
m.topic
as an extension inm.room.topic
to allow for both plain text and HTML rendering of room topics.Eventually most of the logic should be pushed down into matrix-events-sdk (see matrix-org/matrix-events-sdk#5). However, in order not to complicate future architectural changes of this project, @turt2live advised to put the code here for now.
Here's what your changelog entry will look like:
✨ Features